From: Luc Teirlinck Date: Mon, 26 Apr 2004 03:13:43 +0000 (+0000) Subject: (ielm-prompt-read-only, ielm-prompt): Minor doc fix. X-Git-Tag: archive/raspbian/1%29.2+1-2+rpi1~1^2~22930 X-Git-Url: https://dgit.raspbian.org/%22http:/www.example.com/cgi/%22https:/www.github.com/%22bookmarks:///%22http:/www.example.com/cgi/%22https:/www.github.com/%22bookmarks:/?a=commitdiff_plain;h=9afdb1bbf3e78e295ff7a23c12c8fed9fad1dfa9;p=emacs.git (ielm-prompt-read-only, ielm-prompt): Minor doc fix. --- diff --git a/lisp/ielm.el b/lisp/ielm.el index 2eae3591c7f..0a249f65095 100644 --- a/lisp/ielm.el +++ b/lisp/ielm.el @@ -62,7 +62,7 @@ Interrupting the IELM process with \\\\[comint-interrupt-subjob], and then restarting it using \\[ielm], makes the then current default value affect _new_ prompts. However, executing \\[ielm] does not have this effect on *ielm* buffers with a running process. -For IELM buffers that are not called *ielm*, you can execute +For IELM buffers that are not called `*ielm*', you can execute \\[inferior-emacs-lisp-mode] in that IELM buffer to update the value, for new prompts. This works even if the buffer has a running process." :type 'boolean @@ -83,7 +83,7 @@ _default_ value affect _new_ prompts. Unless the new prompt differs only in text properties from the old one, IELM will no longer recognize the old prompts. However, executing \\[ielm] does not update the prompt of an *ielm* buffer with a running process. -For IELM buffers that are not called *ielm*, you can execute +For IELM buffers that are not called `*ielm*', you can execute \\[inferior-emacs-lisp-mode] in that IELM buffer to update the value, for new prompts. This works even if the buffer has a running process." :type 'string